1
00:00:00,390 --> 00:00:06,670
Now we're going to see an interesting protocol that is a pretty good privacy, as the name suggests,

2
00:00:06,870 --> 00:00:10,500
an excellent protocol, and the walking is very simple to understand.

3
00:00:10,800 --> 00:00:17,100
If you have understood the previous cryptography and the public key encryption decryption videos, then

4
00:00:17,220 --> 00:00:20,700
this lecture is going to be a wonderful lecture for you.

5
00:00:21,060 --> 00:00:25,460
Now, in this lecture, I am not going to have any bullet points.

6
00:00:25,470 --> 00:00:28,050
I'm just going to explain through the slides.

7
00:00:29,220 --> 00:00:36,810
So in the early 1990s, Phil Zimmermann, also from M.I.T., that is Massachusetts Institute of Technology

8
00:00:37,170 --> 00:00:45,240
and US, wrote most of the code for his freely available version of public key encryption designed to

9
00:00:45,240 --> 00:00:47,790
encrypt data for email transmission.

10
00:00:48,360 --> 00:00:51,500
PGP is mostly used for email transmission.

11
00:00:51,510 --> 00:00:58,860
Make sure you remember that Zimmerman basically compared email to postcards because anyone can read

12
00:00:58,860 --> 00:01:02,630
e-mail messages traversing the Internet just as they can.

13
00:01:02,640 --> 00:01:05,430
Postcards traveling to the Postal Service.

14
00:01:05,430 --> 00:01:12,330
Right by contrasting, he compared an encrypted message to a letter mailed inside an envelope.

15
00:01:12,720 --> 00:01:16,100
And this is the figure of PGP encryption system.

16
00:01:16,890 --> 00:01:17,760
So don't worry.

17
00:01:17,760 --> 00:01:22,470
I'm going to explain what exactly is now in the figure or you can see on the screen.

18
00:01:22,470 --> 00:01:23,820
Let me take my pen.

19
00:01:24,210 --> 00:01:24,660
Yes.

20
00:01:25,270 --> 00:01:27,800
So the document this is the original document.

21
00:01:27,810 --> 00:01:31,740
OK, now the document is encrypted with a session key.

22
00:01:31,740 --> 00:01:39,860
So let's consider this is a session key, OK, which is then encrypted with the public key of the recipient.

23
00:01:39,890 --> 00:01:40,560
So let's see.

24
00:01:40,560 --> 00:01:48,000
Here is the recipient and his public key is available in this key store because public is a public knowledge.

25
00:01:48,360 --> 00:01:50,070
It is available to everyone.

26
00:01:50,580 --> 00:01:52,560
Now with this public key.

27
00:01:53,250 --> 00:02:01,110
This key is encrypted because we know that whenever you want to send a data over the Internet in order

28
00:02:01,260 --> 00:02:08,010
for the recipient to decrypt the data with his private key, you must encrypt the data with the public

29
00:02:08,010 --> 00:02:13,950
key and then only the public or the private can decrypted.

30
00:02:14,310 --> 00:02:24,240
OK, so now this session is encrypted with the public key of the recipient and this data is also encrypted

31
00:02:24,240 --> 00:02:26,820
with the session key.

32
00:02:27,330 --> 00:02:36,570
And then the encrypted document, along with the encrypted session key with the help of public key is

33
00:02:36,570 --> 00:02:40,080
sent over to the recipient here.

34
00:02:41,040 --> 00:02:44,850
OK, I'll erase it so that you will have a clear picture of.

35
00:02:47,470 --> 00:02:49,270
Oh, yes.

36
00:02:51,150 --> 00:02:56,120
Now, let's see how do we explain the decryption process?

37
00:02:57,080 --> 00:03:03,190
So once again, I will revise the encryption process, you have the document, you have a session with

38
00:03:03,200 --> 00:03:09,890
the help of session key, you encrypt that document and then you end this session with the help of the

39
00:03:09,890 --> 00:03:16,410
public and then this encrypted document, plus encrypted session key.

40
00:03:16,490 --> 00:03:19,440
You sent it over to the recipient here.

41
00:03:20,060 --> 00:03:27,740
Now, when the recipient receives the encrypted document along with the encrypted session key, now,

42
00:03:27,740 --> 00:03:37,360
since this session key is encrypted with the public key of this recipient, it can be easily decrypted

43
00:03:37,370 --> 00:03:41,990
with the help of private keys of the recipient.

44
00:03:42,260 --> 00:03:50,420
So when the recipient decrypt the encrypted key with his private key, he gets the original session

45
00:03:50,420 --> 00:03:50,690
key.

46
00:03:50,690 --> 00:03:52,490
He gets the audience session key.

47
00:03:53,030 --> 00:04:01,580
And with the help of this session key, he then decrypt this document to form the new document to get

48
00:04:01,580 --> 00:04:02,840
the original document.

49
00:04:03,350 --> 00:04:10,940
So in this case, what you have to remember is session key encryption is done using symmetric encryption.

50
00:04:10,940 --> 00:04:15,530
That is the same key for encryption and the same key for decryption.

51
00:04:15,920 --> 00:04:22,610
But in order to transfer the session key over the Internet, automatic encryption is used.

52
00:04:23,090 --> 00:04:27,720
Now, automatic encryption takes a longer time than symmetric encryption.

53
00:04:28,040 --> 00:04:34,790
That is why in order to just transfer the keys, asymmetric encryption is used in most of the today's

54
00:04:34,790 --> 00:04:35,150
world.

55
00:04:35,510 --> 00:04:41,880
But when it comes to encrypting local documents or the symmetric key, encryption is used.

56
00:04:42,320 --> 00:04:47,090
So make sure you remember this is the example of pretty good privacy.

57
00:04:47,120 --> 00:04:47,450
OK.

58
00:04:50,030 --> 00:04:56,500
Now, since the recipient is the only person with the matching private key on the deck and decrypted

59
00:04:56,520 --> 00:05:03,860
session, because there we are using asymmetric key, uh, encryption, uh, for the personal use only.

60
00:05:04,460 --> 00:05:07,520
And the name implies it's really pretty good privacy.

61
00:05:08,090 --> 00:05:10,730
RNC data security that is reversed.

62
00:05:11,000 --> 00:05:17,330
Shamir and Adelman security and the US federal government both had a problem with Zimmermann's product.

63
00:05:17,840 --> 00:05:24,200
Now, the RNC complained about patent infringement and the government actually decided to prosecute

64
00:05:24,200 --> 00:05:27,770
Zimmerman for exporting munitions, great software.

65
00:05:28,460 --> 00:05:34,820
But the government actually dropped the charges against Zimmerman and the licensing fee is paid to Oddisee.

66
00:05:35,240 --> 00:05:40,100
So today, BGB and other public utility products are readily available.

67
00:05:40,100 --> 00:05:48,440
But if you cleverly see this is the most of it actually is a good protocol for encryption and preventing

68
00:05:48,440 --> 00:05:50,330
your data over the direct transfer.

69
00:05:50,810 --> 00:05:57,950
I hope my lectures are very clear to you because I'm trying to explain all those things in very simple

70
00:05:57,950 --> 00:05:59,980
and clear words.

71
00:06:00,410 --> 00:06:06,110
So if you're really enjoying this course, I request you to read Arcus, because if you read articles,

72
00:06:06,110 --> 00:06:13,370
the more ratings we get of you really feel good and can draft more interesting courses to you and you

73
00:06:13,370 --> 00:06:15,800
can, you know, learn a lot from us.

74
00:06:16,370 --> 00:06:21,420
So please read our your feedback is very valuable to us.

75
00:06:21,440 --> 00:06:23,300
I will see you in the next lecture.
